Skip to content

Conversation

@kornelski
Copy link
Collaborator

@kornelski kornelski commented Nov 29, 2024

  1. We're not using it.

  2. Anybody who has so many users that they need a full-blown database, either already has their own DB, or is going to need a lot more user management and administrative features that we're never going to implement. Auth via SSO makes much more sense for big deployments.

  3. The AuthProvider interface doesn't separate auth storage from application logic controlling user access. Whenever we want to change account management/permissions logic, it needs to be implemented in each backend separately, so additional auth backends either bitrot or create extra work.

Note: the postgres-based crate index remains supported. The storage interface doesn't vary as much, and pg can have a better search.

@Noah-Kennedy Noah-Kennedy merged commit 0c0eb18 into main Dec 5, 2024
11 checks passed
@Noah-Kennedy Noah-Kennedy deleted the no-pg-auth branch December 5, 2024 04:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants